-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arm64: fix fvp smp faild to boot #14476
Conversation
[Experimental Bot, please feedback here] This pull request appears to meet the basic NuttX requirements. However, it could be improved with some clarifications: Summary:
Impact:
Testing:
By adding these details, you'll make it easier for reviewers to understand and evaluate your pull request. |
@@ -14,6 +14,8 @@ CONFIG_ARCH_CHIP_FVP_ARMV8R=y | |||
CONFIG_ARCH_CHIP_FVP_R82=y | |||
CONFIG_ARCH_EARLY_PRINT=y | |||
CONFIG_ARCH_INTERRUPTSTACK=4096 | |||
CONFIG_ARM64_SMP_BUSY_WAIT=y |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any idea why FVP needs busy wait?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The FVP SMP startup has always been using the busywait strategy. Before my modification, it serially waited for a fixed global variable (cpu_ready_flag). After I changed it to parallel startup for CPUs (1 to n), I added a wait address for more generality. However, at that time, the FVP SMP was not configured accordingly, leading to this error.
Additionally, let me mention that the arm64 QEMU SMP startup uses the PSCI method, rather than busywait.
reason: we should give a busy wait addr This commit fixes the regression from apache#13640 Signed-off-by: hujun5 <[email protected]>
Summary
fix fvp smp faild to boot
we should give a busy wait addr
This commit fixes the regression from #13640
Impact
arm64 fvp smp
Testing
fvp-armv8r:nsh_smp ostest